New Features and Bugs of Httpproxy

Please note that no pinciple bugs and wanted features mentioned in the provided guide file are listed here but new ones will be added here first.

Another note: I'm writing my so called "Studienarbeit" right now which takes plenty of time. I don't know how much time there's left for improving httpproxy in the next weeks, I'm sorry...

Httpproxy Feature History

Still wanted for one of the next versions

• Better log file format with more information (transmitted bytes, etc).
• Specification of expire and delete timeouts in seconds / minutes / etc... / years.

V0.12 public beta

• Much faster startup.
  When httpproxy is terminated regulary (that is by Ctrl-C or AmiTCP shutdown), it writes its current cache state into a file called .cachetable. On startup this file is read whenever it is found. No cache files are deleted at all in this case, though...
• The guide file now contains a 'Troubleshooting' section. t
• Assertions are now written to the Log- and the Debugfile, too.
• Configurable maximum number for connections ('numreq' option).

V0.11 public beta

• This page was created.
• Rudimentary POST method support.
  URLs using the POST method are proxied to the requested host or to the proxyproxy host in online mode only now. These URLs are *never* ever cached at the moment. For this to work the caching system needs a major rewrite... :-(
• Caches are allocated on request now (no 1024 cache limit any longer).
  It still hope it makes no trouble any more (I got headaches from that f***ing code fragment :-] ...)
• Small, almost negligible speed improvements.
• Compiles fine with AmiTCP4.0 Api now when youe define 'FIXTIME' on invocation of the compiler.

Httpproxy Bug History

V0.12 public beta

• Assertions that like to fail:
  • None yet.
• None known.

V0.11 public beta

• Assertions that like to fail:
  • (cc->File [9] == '@') file httpproxy.c line 897
  • (Req - Requests < MAX_REQUESTS) file httpproxy.c line 1928
• Two people mailed me that httpproxy crashed their computer in online mode on some URLs. I noticed that AmiTCP/netlib is saving hostent ip addresses on odd addresses sometimes which caused a longword read to fail on 68000 machines.
  (fixed in V0.12).
• Httpproxy terminates when more than eight URLs were queued.
  (fixed in V0.12)
• Sometimes httpproxy terminates in online mode when it is not desired. I found one wrong assertion that could fail for non-conformant http-requests, I hope that was all.
  (fixed in V0.12 (I hope))
• Requests that need Authorization are not processed correctly right now, because error messages are cached. Just enter your user name and password and press Reload immedeately after getting the error message.
  (not yet fixed)
• Interrupted requests that are not complete can lock up a request slot (there are eight at the moment). Almost nobody should notice anything about this (only internal).
  (almost fixed in V0.12 (I hope))

V0.9 public beta

• Assertions that like to fail:
  • (ccc->Flags & CACHE_VALID) file httpproxy.c line 820 ?!? I don't remember it...
• Requests longer than 1 KByte are not handled correctly right now. This includes requests from the popular beta 1 version of AMosaic V2.0. The beta 3 version does not send these rather long requests.
  (fixed in V0.10 beta)
• Many servers have difficulties in parsing full URL requests but only allow local object requests. When Httpproxy is used in proxyproxy mode this bug won´t be noticed.
  (fixed in V0.11 beta)
• When a cache file is to be deleted, an assertion could fail. Set deletetime to a high value to work around this.
  (fixed in V0.11 beta)